bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Thu, 11 Jul 2019 06:39:38 +0000 (07:39 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Thu, 11 Jul 2019 06:39:38 +0000 (07:39 +0100)
commitda6f19fa16dbc68c555040153c0d6891038275d4
tree3ac3c2e22c3dc71857ffe6e44f687eb4aee0c82e
parent6750c12a036f3aadb6046a9e777b23936fd92b2e
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h